-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature/bump mlx #75
Feature/bump mlx #75
Conversation
add note to README
fix memory selection
# Conflicts: # Package.swift # Sources/SpeziLLMLocal/LLMLocalSchema.swift # Sources/SpeziLLMLocal/LLMLocalSession+Generate.swift # Sources/SpeziLLMLocal/LLMLocalSession+Setup.swift # Tests/UITests/TestAppUITests/TestAppLLMLocalUITests.swift
@LeonNissen #78 tackles a breaking change from the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @LeonNissen for the great PR! 🚀 Great to see that SpeziLLM is continuously moving forward!
I had some thoughts in-line, feel free to follow up on them, then we can merge the PR soon (especially in order to fix e.g. #77)
Regarding the failing patch test coverage: No need to worry about that!
Update: As SpeziLLM currently doesn't compile at all (because of the MLX semantic versioning issue described above), I pinned the MLX library versions to specific versions in #80
Please take that into consideration when pinning your MLX dependencies!
Sources/SpeziLLMLocal/Helpers/LLMContext+formatForTransformersChat.swift
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the review @philippzagar! Made some small changes to the tagged versions to clarify semantic versioning expressiveness in the Package file; thank you for all the feedback!
Thanks @PSchmiedmayer for looking into that! And yes, the |
@philippzagar The constraint on the |
Oh I see, was a bit confused as well about that.. |
Thank you so much for you in-depth feedback! Lets just discuss the final comments and finish up to tag a new version 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for incorporating the feedback @LeonNissen. 🚀
As mentioned, there are definitely some points in there that we should make a bit more flexible and documented in the future, but they are definitely fine for now!
Awesome, thank you, @philippzagar! Your feedback has truly improved the PR 🥇 |
# *Update MLX Version* ## ⚙️ Release Notes **Breaking Changes**: This pull request introduces additional breaking changes. Version Updates: - mlx-swift has been updated to version 0.18.1. - mlx-swift-examples has been updated to version 1.18.1. - `LLMLocalSchema` can now be update with other parameters. - The `ChatTemplate` used by `swift-transformers` can be overwritten. - The `LLMContext` can be overwritten with a custom context (`[[String: String]]`). ## 📝 Code of Conduct & Contributing Guidelines By submitting creating this pull request, you agree to follow our [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md): - [x] I agree to follow the [Code of Conduct](https://github.com/StanfordSpezi/.github/blob/main/CODE_OF_CONDUCT.md) and [Contributing Guidelines](https://github.com/StanfordSpezi/.github/blob/main/CONTRIBUTING.md). --------- Co-authored-by: Leon Nissen <> Co-authored-by: Paul Schmiedmayer <[email protected]>
Update MLX Version
⚙️ Release Notes
Breaking Changes: This pull request introduces additional breaking changes.
Version Updates:
LLMLocalSchema
can now be update with other parameters.ChatTemplate
used byswift-transformers
can be overwritten.LLMContext
can be overwritten with a custom context ([[String: String]]
).📝 Code of Conduct & Contributing Guidelines
By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines: